One of the most-hyped features of Windows 95 is its 32-bit architecture. But are 32 bits twice as good as 16? Or are they 2 to the 16th power as good? Are 32-bit applications better than 16-bit code? Well, yes and no.
There is nothing magical about the number 32; in fact, many applications that claim to have 32-bit code may work even slower than their 16-bit counterparts. Theoretically, 32-bit programming can improve performance, but in practice, many factors affect whether or not 32-bit architecture will be a boon or a bust for any particular application.
Lets take a look at a few of the attributes of 32-bit code:
Memory Mapping
Memory mapping allows the operating system to access large files as a single block of memory, instead of as a series of smaller blocks. An application which handles large files can benefit from using this feature.
Pre-emptive Multitasking
Windows 95 allows your CPU to switch more seamlessly and reliably between 32-bit applications. 16-bit applications use cooperative multitasking, which can increase waiting time and occasionally hang a program when the operating system becomes confused about which application is controlling the CPU.
Multithreading
Multithreading allows an application to run more than one section of executable code at a time. For many programs this simply might mean the ability to print in the background. 16-bit applications cannot multithread, therefore applications that need to accomplish diverse tasks simultaneously can benefit from 32-bit coding.
Thunking
Thunking is the word used to describe what happens when an operating system switches between 32-bit and 16-bit code. Thunking slows down performance, so, theoretically, your computer running Windows 95 will perform better when it is exclusively running 32-bit applications.
